Add support for Sentry monitoring #283
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pvannierop
force-pushed
the
feature/sentry
branch
from
dcc8b8c to
5fd4a0f
Compare
Includes addition to documentation.
pvannierop
force-pushed
the
feature/sentry
branch
from
0ba5657 to
bd18846
Compare
…thorizer-app-backend
pvannierop
force-pushed
the
feature/sentry
branch
from
b1b4409 to
575199e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description: This PR will add option to monitor the application with Sentry. Sentry monitoring will be enabled by the following:
SENTRY_DSNenvironment variable that points to the desired Sentry DSN.SENTRY_LOG_LEVELenvironment variable to control the minimum log level of events sent to Sentry.The default log level for Sentry is
ERROR. Possible values areTRACE,DEBUG,INFO,WARN, andERROR.The docs were updated with these instructions.